Modular base station

ABSTRACT

Disclosed herein are embodiments including a modular base station that is, for example, easily deployable in emerging markets. The modular base station is designed to be easily transported and affixed, for example, to poles or trees. The modular base station is designed to withstand high temperatures caused by operating at high altitudes and to be easily configured, oriented, and serviced in the field. Its components (e.g., radio frequency (RF) circuit boards) are modular so as to interoperate with various third-party compatible devices.

CROSS-REFERENCE TO RELATED APPLICATIONS

This divisional application claims the benefit of and priority to U.S.Provisional Application No. 62/297,779, filed on Feb. 19, 2016, entitled“MODULAR BASE STATION,” U.S. Provisional Application No. 62/351,827,filed on Jun. 17, 2016, entitled “MODULAR BASE STATION,” and U.S.Non-Provisional application Ser. No. 15/433,828, filed on Feb. 15, 2017,entitled “MODULAR BASE STATION,” all of which are hereby incorporated byreference in their entireties.

TECHNICAL FIELD

The disclosed teachings relate to a communications network base station.The disclosed teachings more particularly relate to systems, devices,and methods related to a base station that has modular elements.

BACKGROUND

Many households around the world, including in emerging markets, ownmobile phones commonly referred to as “feature phones,” which are aclass of low-end mobile phones that have limited capabilities incontrast to modern “smartphones.” Feature phones typically provide voicecalling and text messaging functionality but lack modern networkconnectivity (e.g., Internet) capabilities. In contrast, smartphones caninclude advanced mobile operating systems that combine features ofpersonal computer operating systems with advanced network connectivityfeatures for mobile or handheld use. Some feature phones allow for basicmultimedia and Internet capabilities, and may even incorporate supportfor 3G connectivity, touchscreens, and access to popular socialnetworking services.

Feature phones are marketed as a lower-cost alternative to smartphones,especially in emerging markets. In recent years, manufacturers havebegun to produce and sell low-cost smartphones in an effort to tap intomarkets where adoption of high-end smartphones has been low. However,even though these phones may support features such as limited Internetcapabilities, the infrastructure (e.g., ground base stations) to supportthese more advanced capabilities is, for the most part, absent fromthese markets. Moreover, installing conventional infrastructures remainscost prohibitive. Consequently, billions of people lack access to modernnetwork technologies such as the Internet. Moreover, in some markets, itis cost prohibitive to install ground-based copper or other wiring andso these markets are suited for moving directly to cellularcommunications. In cellular communications, a base station typicallyprovides wireless access using various protocols (e.g., LTE, GSM, Wi-Fi)to customer equipment (e.g., cellular telephones). Accordingly, a needexists for systems, devices, and methods for cost-efficient basestations.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows the front and top of the modular base station (MBS) inaccordance with an embodiment of the present technology, wherein the MBSis shown mounted to an external pole;

FIG. 2 shows the bottom of the MBS of FIG. 1 shown removed from the poleaccording to some embodiments of the present disclosure;

FIG. 3 shows the bottom of the MBS of FIG. 2 shown mounted to a poleaccording to some embodiments of the present disclosure;

FIGS. 4A and 4B show a mounting bracket of FIG. 1 shown removed from thebody of the MBS and configured for securing the MBS to a pole or othermounting structure according to some embodiments of the presentdisclosure;

FIGS. 5A and 5B show the mounting bracket mounted to a pole according tosome embodiments of the present disclosure;

FIG. 6 shows a mechanism used to secure a removable plate to themounting bracket according to some embodiments of the presentdisclosure;

FIGS. 7A through 7C show semi-transparent views of the MBS mounted to apole according to some embodiments of the present disclosure;

FIG. 8 shows an enlarged partial front-bottom view of the MBS thatincludes a heatsink according to some embodiments of the presentdisclosure;

FIG. 9 shows a top plan view of the MBS of FIG. 8 according to someembodiments of the present disclosure;

FIG. 10 shows an outer enclosure of the MBS according to someembodiments of the present disclosure;

FIG. 11 shows a semi-transparent top plan view of the MBS according tosome embodiments of the present disclosure;

FIG. 12 shows a lateral cutaway of the MBS with a semi-transparent viewof an inner enclosure according to some embodiments of the presentdisclosure;

FIG. 13 shows a lateral cutaway of the MBS with a semi-transparent viewof the outer and inner enclosures according to some embodiments of thepresent disclosure;

FIG. 14 shows a semi-transparent view of the MBS of FIG. 9 according tosome embodiments of the present disclosure;

FIGS. 15A and 15B are enlarged partial isometric views showing a frontcavity of the MBS formed from the outer enclosure, the door frame, andthe door, shown removed from the MBS according to some embodiments ofthe present disclosure;

FIG. 16 shows an isometric view of an embodiment of the MBS including adoor frame with perforated mesh around the door;

FIG. 17 shows an isometric view of the MBS with the door in a closedposition according to some embodiments of the present disclosure;

FIG. 18 shows the MBS of FIG. 17 with the door in an open positionaccording to some embodiments of the present disclosure;

FIG. 19 shows an embodiment of the MBS with cable grooves formed in thelower portion of the door frame according to some embodiments of thepresent disclosure;

FIGS. 20A and 20B are enlarged isometric views of a front portion of theMBS of FIG. 19 with the cable grooves in the door frame according tosome embodiments of the present disclosure;

FIG. 21 shows an interface and light status system of the MBS accordingto some embodiments of the present disclosure;

FIG. 22 shows labels for the interface of the MBS according to someembodiments of the present disclosure;

FIG. 23 is an exploded view of a portion of the MBS according to someembodiments of the present disclosure;

FIG. 24 shows a perspective view of electronics included in the MBSaccording to some embodiments of the present disclosure;

FIG. 25 shows a lateral view of the electronics included in the MBSaccording to some embodiments of the present disclosure;

FIG. 26 is a block diagram of a general-purpose baseband computing (GBC)circuit board of the MBS according to some embodiments of the presentdisclosure;

FIG. 27 is a block diagram of a front panel, power supply, andhousekeeping microcontroller of the GBC board according to someembodiments of the present disclosure;

FIG. 28 is a block diagram of the front panel, the power supply, thehost processor, and the housekeeping microcontroller of the GBC boardaccording to some embodiments of the present disclosure;

FIG. 29 is a table that represents rules for switching between powersources to feed a load and charge the internal and external batteriesaccording to some embodiments of the present disclosure;

FIG. 30 is a system diagram depicting communications between servers anda mobile device via the MBS according to some embodiments of the presentdisclosure;

FIG. 31 is a block diagram depicting a client device interacting with acloud component according to some embodiments of the present disclosure;

FIG. 32 is a flowchart for synchronizing one or more client devices witha cloud component according to some embodiments of the presentdisclosure;

FIG. 33 is a block diagram depicting multiple sets of client deviceseach having a common base station component (e.g., client softwareinstance) according to some embodiments of the present disclosure;

FIG. 34 is a flowchart for synchronizing sets of client devices with thecloud component according to some embodiments of the present disclosure;and

FIG. 35 is a block diagram of a computer operable to implement thedisclosed technology according to some embodiments of the presentdisclosure.

DETAILED DESCRIPTION

Disclosed herein are embodiments including a modular base station(hereinafter “MBS”) that is, for example, easily and quickly deployablein a cost-effective manner. The MBS is designed to be easily transportedand affixed, for example, to poles, trees, or other suitable supportstructures. The MBS may be designed to withstand extreme environmentalconditions, such as high temperatures that can occur when the MBS isoperating at high altitudes, and to be easily configured, oriented, andserviced in the field by a non-technical person (hence, it may requirenear-zero management).

The components of the MBS can include a general-purpose and basebandcomputing (GBC) component and a radio frequency (RF) component withintegrated analog front-end for GSM and LTE. The components of the MBScan be modular so as to interoperate with various third party compatibledevices. In addition to its functionality, the MBS can have anaesthetically pleasing ornamental appearance, such as is disclosed incommonly assigned U.S. Design patent application No. 29/555,287, titledCommunications Base Station, filed concurrently herewith, and which isincorporated herein in its entirety by reference thereto.

In some embodiments, the MBS is low-cost, low-power and easy-to-managecellular access point (e.g., a “network-in-a-box”). The MBS may support,for example, LTE or GSM (SMS/voice/GPRS/Edge) for rural settings (e.g.,emerging markets). Moreover, it has a modular design which can support a1/2/4 Transceiver (TRX) in quad-band fashion, in multipleconfigurations. Further, the MBS can support various deploymentscenarios, including (i) network-in-a-box, (ii) remote radio head (RRH),(iii) small cell with centralized core, and so forth. For the GSM stack,the disclosed technology can support/run either closed source or opensource (e.g., Osmo/OpenBTS). The MBS can also be configured to support3G/LTE for a number of users (e.g., a maximum of 32 users).

As detailed below, the disclosed technology can improve network accessfor rural communities and can be operated by a local user who has nospecialized technical skills in operating or configuring communicationsequipment. The MBS may be designed to be durable under variouscircumstances. For example, in particular embodiments, the MBS includesa multi-enclosure structure that protects sensitive internal electronicsfrom the elements and other harsh conditions, while maintaining theflexibility of a modular design. In addition, the MBS can use differentpower supplies and can automatically switch from one power supply toanother to provide an uninterrupted power supply. The disclosedtechnology may also include a mounting bracket that allows the MBS to beeasily attached to a mounting structure, such as a pole, post, rail,tree, or other suitably stable support member.

The MBS can include antennas that can change between omni-directionaland directional configurations by simply adjusting a metal plate. Inaddition, in some embodiments, a Base Station System (BSS) of the MBS isquad-band and may use redundancy of power amplifiers to provideuninterrupted service while remaining flexible. Also, the MBS mayinclude out-of-band control channels (OOBCCs) to allow access to an MBSremotely from anywhere. The disclosed technology also includes“clocking” to take in GPS input and other data to generate usefulinformation. Lastly, the disclosed technology includes mechanisms formaintaining a reliable and uniform system of MBSs by providing, forexample, mechanisms to synchronize the MBSs with each other andcloud-based (e.g., Internet) servers or services.

The embodiments set forth below represent the necessary information toenable those skilled in the art to practice the embodiments, andillustrate the best mode of practicing the embodiments. Upon reading thefollowing description in light of the accompanying figures, thoseskilled in the art will understand the concepts of the disclosure andwill recognize applications of these concepts that are not particularlyaddressed herein. It should be understood that these concepts andapplications fall within the scope of the disclosure.

The purpose of terminology used herein is only for describingembodiments and is not intended to limit the scope of the disclosure.Where context permits, words using the singular or plural form may alsoinclude the plural or singular form, respectively.

As used herein, unless specifically stated otherwise, terms such as“processing,” “computing,” “calculating,” “determining,” “displaying,”“generating” or the like refer to actions and processes of a computer orsimilar electronic computing device that manipulates and transforms datarepresented as physical (electronic) quantities within the computer'smemory, or registers into other data similarly represented as physicalquantities within the computer's memory, registers, or other suchstorage medium, transmission, or display devices.

As used herein, the terms “connected,” “coupled,” or variants thereof,mean any connection or coupling, either direct or indirect, between twoor more elements. The coupling or connection between the elements can bephysical, logical, or a combination thereof.

FIG. 1 shows an example of the front and top of an MBS 10 mounted to apole 12, which is external to the MBS 10. FIG. 2 shows an example of thebottom of the MBS 10 removed from the pole 12. FIG. 3 shows an exampleof the bottom of the MBS 10 illustrated in FIG. 2 mounted to the pole12. As shown, the MBS 10 is a physical device that a person in the fieldcould install to provide, for example, VoIP services to people in aregion covered by the MBS 10 (e.g., a region within wirelesscommunication range of the MBS 10).

The MBS 10 of some illustrated embodiments also utilizes a mountingstructure (e.g., mounting bracket 14) attachable to pole 12 or othersupport structure and adapted for quick and easy attachment of the MBS10 to the support structure. For example, FIGS. 4A and 4B show anexample mounting bracket 14 for securing the MBS 10 to a supportstructure such as a 2-4″ mounting pole). The illustrated mountingbracket 14 has two sides that form a 90° angle. The bracket is formed oftwo separate pieces: an engagement member 16 that attaches to the pole12, and a separate plate 18 that securely attaches to the MBS 10 andremovably attaches to a holster portion 20 of the engagement member 16.

The removable plate 18 can include screw mounts or other suitablefasteners used to attach the plate 18 to the MBS 10. The removable plate18 then may slide into (or out of) the mounting bracket 14's holster 20in the directions of the arrow shown on FIGS. 4A and 4B. Accordingly,the MBS 10 is movable between installed and removed positions relativeto the engagement member 16 and the pole 12 or other support structureby sliding the removable plate 18 attached to the MBS 10 into or out ofthe holster 20, respectively. As such, the mounting bracket 14 caneasily be attached to a pole 12, and the MBS 10 can easily be attachedto the mounting bracket 14. Moreover, the mounting bracket 14 allows forone-handed installation. In addition, in some embodiments the bracket 14is durable such that it can, for example, sustain at least a Category 5hurricane.

FIGS. 5A and 5B show an example embodiment of the mounting bracket 14mounted to the pole 12. As shown, four U-bolts 22 are used to attach themounting bracket 14 to the pole 12. The 90° angle of the bracket 14allows a user to easily tighten the U-bolts 22 while facing the side ofthe bracket 14 that accepts the MBS 10.

FIG. 6 shows an example mechanism used to secure a removable plate 18 tothe mounting bracket 14. As shown, a latch 24 is used to releasablyretain the removable plate 18 in the holster 20 of the mounting bracket14, thereby securely retaining the associated MBS 10 in the installedposition on the mounting bracket 14. In one embodiment, the latch 24 ismoved relative to the holster 20 to an unlatched position, whereby thelatch 24 does not interfere with the removable plate 18 sliding into theholster 20. The latch 24 may be rotated in the direction of the curvedarrow to a latched position (as seen in FIG. 6) so the latch 24 isimmediately adjacent to the removable plate 18 and in an orientationthat physically blocks the plate 18 from sliding out of the holster 20.The latch 24 can be spring loaded or otherwise biased toward the latchedposition. The mounting bracket 14 can include a locking screw 26attached to the latch 24 and configured to be tightened to engage theend of the holster 20 and securely retain and lock the removable plate18 in the installed position.

The removable plate 18 of the illustrated embodiment includes a handlemember, such as one or more hooks 28 that a user can grasp to provideleverage for moving the removable plate 18 and MBS 10 between theremoved and installed positions by pulling or pushing on the hooks 28,thereby sliding the plate 18 in and out of the holster 20. The hooks 28can be of any size to serve a variety of purposes. For example, largerhooks could facilitate carrying the MBS 10 and/or could be used as astand for the MBS 10 to sit atop a flat surface. As such, a hook couldbear the weight of the MBS 10. Alternatively, a strap (not shown) couldbe used to pass through smaller hooks such that the strap could be usedto carry the MBS 10. As shown, the hooks 28 are secured to the removableplate through one or more slots 30.

The slots 30 may serve multiple purposes as well. For example, the slots30 can be used to attach the MBS 10 to a support structure of anysuitable size (e.g., a large tree). In particular, in some embodiments,the removable plate 18 includes one or more slots 30 that can accept astrap. As such, the removable plate 18 can be fastened to an object ofany suitable size or shape with a strap passing through the slots 30 ofthe removable plate 18. In addition, a strap can be used to carry theplate 18 and associated MBS 10 when an operator is climbing the pole 12.Moreover, the slots 30 provide a redundant mechanism to secure the MBS10 to the pole 12 in addition to using the mounting bracket 14. The MBS10 can be attached to a flat surface by screwing the holster 20 to theflat surface. In at least one embodiment, the removable plate 18 can befixed directly to the flat surface or other mounting structure and thenthe MBS 10 can be connected to the removable plate 18.

FIGS. 7A through 7C show semi-transparent views of examples of the MBS10 mounted to the pole 12. In particular, FIG. 7A shows an isometricview of an example of a semi-transparent MBS 10 that is attached to apole 12; FIG. 7B shows a side elevation view of an example of thesemi-transparent MBS 10 attached to a pole 12; and FIG. 7C shows abottom plan view of an example of a semi-transparent MBS 10 attached toa pole 12.

The MBS 10 may optionally include a heatsink coupled to internalelectrical components within the body of the MBS 10 to carry heat awayfrom the MBS 10's interior areas. The heatsink may be a modularcomponent that can be included in the MBS 10. For example, FIG. 8 showsan example of a bottom isometric view of the MBS 10 including a heatsink32 projecting from the bottom surface of the MBS 10's body. The heatsink32 allows for natural convection to help carry heat away from the MBS10, thereby cooling the internal components of the MBS 10. The heatsink32 of the illustrated embodiment includes several fins and a cutout forthe mounting bracket 14, although other embodiments can utilize otherheatsink configurations. In various embodiments, the heatsink 32 can beattached to the internal electrical components via a surface (e.g.,bottom or side surface) of the MBS or other means.

The disclosed embodiments may include MBSs of different dimensions. Forexample, FIG. 9 shows an example of a top view of a tall (i.e., longer)MBS 10. As such, the MBS 10 of FIG. 1 may be “shorter” (e.g., 14 inches)compared to the taller MBS 10 (e.g., greater than 19 inches) of FIG. 9.The shorter MBS 10 of FIG. 1 might not include certain componentsincluded in the taller MBS 10 of FIG. 9; for example, the MBS 10 of FIG.1 may not include any internal antennas, whereas the taller MBS 10 ofFIG. 9 may include two internal antennas.

Embodiments of the disclosed MBS 10 include structural features that mayallow for sustained and reliable operations in harsh environments andacross a large range of temperatures and altitudes. Conventional basestations, in contrast, have limited operational capabilities and tend tobreak down relatively quickly.

The MBS 10 of the illustrated embodiment includes an outer enclosure(i.e., shell) that covers and protects a durable inner enclosure. Forexample, FIG. 10 shows an example of an outer enclosure 34 of the MBS10. The outer enclosure 34 is a modular element that can be readilyremoved and/or replaced. FIG. 11 shows an example of a semi-transparentview of MBS 10 including the inner enclosure 36. The inner enclosure 36may have any suitable length, including, for example, a length of abouthalf of the length of the outer enclosure 34. The inner enclosure 36 isalso a modular component that can be readily removed and/or replaced.The inner enclosure 36 houses electronics and other components that may,for example, be sensitive to environmental conditions. The innerenclosure 36 can also be connected to the heatsink 32 to carry heat awayfrom the interior of the inner enclosure 36 and the associated internalcomponents.

FIGS. 12 through 14 show examples of the structural features of the MBS10 relative to internal components. In particular, FIG. 12 shows alateral cutaway of an embodiment of the MBS 10 with a semi-transparentview of an inner enclosure 36. FIG. 13 shows a lateral cutaway of anembodiment of the MBS 10 with a semi-transparent view of the outerenclosure 34 and inner enclosure 36. FIG. 14 shows a semi-transparentview of an embodiment of the MBS 10.

The outer enclosure 34 may be formed of plastic or other durablematerial that will have minimal interference with one or more antennas38 located internal to the outer enclosure 34, and outer enclosure 34may operate as a buffer between the ambient environment and the innerenclosure 36 that houses, for example, a number of circuit boards and/orother components. The outer enclosure can include vents 40 adjacent toan antenna plate 42 for allowing airflow through the MBS 10 (i.e.,instead of being sealed). This allows the MBS 10 to operate across alarge range of temperatures and altitudes. For example, in particularembodiments, the MBS 10 can operate at temperatures between −40° C. and55° C., and at elevations of up to approximately 20,000 feet or morebecause the design of the MBS 10 allows for greater airflow through theMBS 10 for cooling. In particular embodiments, the MBS 10 can toleratethe increase in internal ambient temperature caused by increasingaltitudes. (e.g., at least 3° C. for every 1,000 feet). The outerenclosure 34 may also act as a solar shield.

As such, the MBS 10 can be deployed in regions such as Afghanistan,Northern India, the Himalayas, and other parts of Central Asia, whichcurrently lack access to reliable base stations due in part to theiraltitudes. Moreover, the disclosed MBS 10 can be deployed at highaltitudes without malfunctioning due to, for example, leakage or seepingof fluid (e.g., rain) into the MBS.

The outer enclosure 34 also protects the inner enclosure 36 fromphysical impacts. For example, the outer enclosure 34 may be designed tocrack or break due to impact caused by falling on the ground; the outerenclosure 34 absorbs some of the impact loads, helping to ensure thatthe inner enclosure 36 can remain intact. As such, only the outerenclosure 34 would need to be replaced in such a fall, which can be doneeasily due to its modular design.

FIGS. 15A and 15B show examples of a front cavity 44 of the MBS 10. Asshown, the cavity 44 is formed from three separate pieces: the outerenclosure 34, a door frame 48, and a door 46 that are assembled to formthe front of the MBS 10. As discussed further below, the cavity 44houses an interface with connectors coupled to the electronic componentsincluded in the inner enclosure 36.

The MBS 10 may be both durable and breathable (e.g., permeable to airand liquids). For example, FIG. 16 shows a view of the MBS 10 of anembodiment including a perforated mesh 50 around the perimeter of thedoor frame 48. As such, the outer enclosure 34 is permeable to fluid(e.g., airflow) through the perforated mesh 50 while the inner enclosure36 may be completely sealed from outer elements. For example, moisturethat seeps into the MBS 10 through the outer enclosure 34 can exitthrough the perforated mesh 50 at the front of the MBS 10 withoutaffecting the electronics contained in the inner enclosure 36.

Referring back to FIGS. 12 through 14, these embodiments of the MBS 10include one or more antennas 38. As shown, antenna 38 is housed in theportion of MBS 10 that is external to the inner enclosure 36 butenclosed by the outer enclosure 34. Each antenna 38 may be a flatsurface suspended by four pyramidal-type pillars. This configuration ofpillars helps to minimize contact with each antenna 38 and provides adistance between the removable antenna plate 42 located on the bottom ofthe MBS 10. In some embodiments, the MBS 10 may include any number ofantennas that may, for example, have a side-by-side configuration (i.e.,are co-planar). The antennas could be jointly steered (or passive) tooperate in conjunction with the removable plate 42.

Referring specifically to FIG. 14, the antenna plate 42 reflects signalsto allow the one or more antennas 38 to operate as an omni ordirectional antenna depending on whether the antenna plate 42 isinserted in the MBS 10. The antenna plate 42 is connected to the outerenclosure 34 to form a bottom portion of the MBS 10 adjacent to theheatsink 32. As indicated above, the outer enclosure 34 can includevents 40 adjacent to the antenna plate 42. The antenna plate 42 can besecured to the MBS 10 with screws or other fasteners, so the antenna 38is protected within the interior area defined by the outer enclosure 34and the antenna plate 42. The antenna 38 is configured as a directionalantenna while the plate 42 is inserted into the back of the MBS 10, andthe antenna 38 is configured as an omni antenna while the plate 42 isremoved from the back of the MBS 10. As such, the multiple antennascould be jointly steered (or passive) to operate in conjunction with theremovable plate 42 as omni or directional antennas.

The ability to configure the one or more antennas 38 as omni ordirectional antennas is another modular aspect of the MBS 10, whichallows for tuning performance depending on a region where the MBS 10 isdeployed and what configuration of a signal would be desirable. Forexample, the antenna 38 could be configured as an omni antenna if theMBS 10 is deployed in the middle of a valley and the client equipmentwas in all directions around the MBS 10.

The pillars may sit atop a dome structure formed, in part, by the vents40, and each antenna 38 may be suspended by the pillars that sit atopthe dome structure. As such, air can flow in through the perforated mesh50, over the inner enclosure 36, and out of the vents 40 (andvice-versa) to provide cooling (augments cooling by the heatsink 32).

As indicated above, the MBS 10 includes a cavity 44 that housesconnectors for interfacing with the MBS 10. The door 46 enclosing thecavity 44 can be opened to access the connectors and closed to securethe connectors from the environment. For example, FIG. 17 shows anexample of the door 46 of the MBS 10 in a closed position fully closingthe opening in the door frame 48. FIG. 18 shows an example of the door46 in an open position, thereby providing access into the cavity 44through the opening in the door frame 48 of the MBS 10. As such, thedoor 46 can be opened to connect components housed in the innerenclosure 36 to components external to the outer structure 34.

As shown, the door 46 on the front of the MBS 10 acts as a barrierbetween an ambient environment and the cavity 44 that includesconnectors (e.g., IP-rated connectors) of an interface 52 for connectingto external devices. The cavity 44 has a recessed portion 54 that leadsto cable grooves 56 for cables that extend from the cavity 44 toexternal devices. For example, FIG. 19 shows an example of the cablegrooves 56 and door hinges 58 of the open-door structure of FIG. 18.FIGS. 20A and 20B show examples of progressively larger views of cablegrooves 56 of the MBS 10, respectively.

Specifically, in the example embodiment illustrated in FIGS. 20A and20B, the MBS 10 includes five cable grooves 56 formed on the door frame48. The grooves 56 may be of different sizes for accepting cords (e.g.,cables) of different sizes. As shown, the cable grooves 56 accept N-Type1, RJ45s (RJ-1, RJ-2), N-Type 2, and power cables. As such, for example,an N-Type cable can run from the N-Type connector on the interface 52through the N-Type-sized groove to the external environment.

The use of cable grooves 56 may reduce strain on the cables. Forexample, conventional devices include connectors on an outer shell. Thiscan cause strain on the cables coupled to the connectors (e.g., due toforces (e.g., gravity) pulling on the cables). In contrast, the cablegrooves 56 of the MBS 10 may relieve such strain on the cables. Thisconfiguration may also reduce costs because special-purposeenvironmentally insensitive components (e.g., RJ45 connectors) are notnecessarily required for functioning.

As shown, the door frame 48 includes hinges 58 that attach the door 46to the door frame 48. The hinges 58 allow the door to pivot open andclosed. The hinges 58 also avoid straining a user attempting to installdevices to the interface 52 of the MBS 10 by acting to keep the door 46attached to the MBS 10 while the user is connecting devices to theinterface 52. The door 46 also includes a latch 60 on the side oppositeto the hinges 58 to secure the door 46 when closed.

FIGS. 21 and 22 show an example embodiment with a number of connectors68 on the interface 52 for connecting the electronics of the MBS 10 toexternal devices. In particular, FIG. 21 shows an example of theinterface 52 and light status system of the MBS 10, and FIG. 22 showsexample labels for the interface 52 of the MBS 10.

As shown, the interface 52 includes components such as a legend 64 forthe light status system, a power button 66, and connectors 68 (e.g.,N-Type 1, N-Type 2, RJ-1, RJ-2, and a group of power connectors). Thetwo N-Type connectors (68-1 and 68-2) allow for connecting externalantennas to the MBS 10. The external antennas could replace or augmentthe functions of one or more internal antennas 38. For example, softwareincluded in the MBS 10 could control switching operations between theinternal antennas 38 and any external antennas.

The illustrated example interface 52 also includes RJ45 connectors (RJ-1(68-3) and RJ-2 (68-4)). The RJ-1 connector 68-3 could be utilized tosupply power to the MBS 10 (e.g., Power-over-Ethernet (PoE)), and theRJ-2 connector 68-4 could be utilized to supply power from the MBS 10 toan external device (e.g., another MBS 10). For example, the RJ-2connector 68-4 could be utilized to charge a mobile device or any othersuitable device. Further, an injector could be utilized to compensatefor losses due to devices located, for example, greater than 100 metersfrom the MBS 10.

The interface 52 also includes a 5-pin connector 68-5 to provideconnections for external power sources. Examples of external powersources include solar and external batteries. Specifically, two of thefive pins could be for external power sources. The power could a be a 24Volt DC source obtained from a solar panel. Two of the remaining threepins could be for an external battery, and the last pin could be formonitoring the external battery (e.g., lithium battery) for powermanagement purposes. For example, the MBS 10 could monitor thetemperature of the external battery and respond accordingly withcorrective actions. In some embodiments, the MBS 10 could monitor thecharge status of the external battery and extract power from the solarpanel to charge the external battery when desirable.

As such, the MBS 10 may have multiple, redundant power sources tomaintain an uninterrupted power supply (UPS). For example, the MBS 10may include a power management system to monitor and control both thepower sources and the external devices that utilize the power sources toextract power. For example, the power management system could set apreference for DC power over PoE but rely on PoE if the DC power isunavailable (e.g., external battery and solar power are unavailable).Details about the power management system and its operations forproviding a UPS by switching between appropriate power sources aredescribed further below.

The connectors 68 of the interface 52 may be positioned to facilitateease of connecting cables to the interface 52 by hand. For example,N-Type connectors (68-1 and 68-2) are located in the middle area of theinterface, and RJ-1 connector 68-3 and RJ-2 connector 68-4 are locatedcloser to the boundary of the interface 52 (e.g., above the N-Typeconnectors 68-1 and 68-2). This configuration allows for a person's handto fit into the cavity 44 to screw in the N-Type connectors 68-1 and68-2, and plug in the RJ-1 and RJ-2 connectors 68-3 and 68-4.

The recessed portion 54 of the cavity 44 also facilitates a hand to fitinto the cavity 44 even when rigid cables are connected to the interface52 because the cables are routed along the recessed portion 54. Forexample, a person can screw in a first N-Type connector 68-1, route itthrough the recessed portion 54, and secure it to a first cable groove56-1. The person can then connect a second N-Type connector 68-2 in asimilar manner with minimal obstruction by the cable of the first N-Typeconnector 68-1.

Referring back to FIG. 21, the MBS 10 includes a light status systemutilized to signal a status or event of the MBS 10 to persons local tothe MBS 10. As shown, the light status system includes a configurationof multiple light sections 70 that may form any suitable shape,including the illustrated “U” shape on the front of the MBS 10.Specifically, the three light sections 70-1, 70-2, and 70-3 are locatedon the perimeter of the door frame 48.

The light status system is a mechanism for signaling the status of theMBS 10 to persons that are located within line-of-sight (e.g., within adistance such as five kilometers) from the MBS 10 (e.g., a person on theground away from a pole-mounted MBS 10). A combination of the variablelight shape, colors, and patterns (e.g., circulating, pulsing, orflashing) of the light status system can effectively communicate avariety of readily understandable information to persons on the ground.

In the example embodiment shown, the light status system uses red andgreen colors to illuminate the three light sections 70 in accordancewith different patterns used to signal the status of the MBS 10. Theleft light section 70-1 communicates the status of the radio, and theright light section 70-3 communicates the status of the backhaul.Specifically, a green circulating pattern signals a “booting up” status;a green pulsing pattern signals a “running normal” status; a red pulsingpattern signals an “error encountered” pattern; a red, left flashpattern signals a “radio failure” status; and a red, right flash patternsignals a “backhaul failure.”

FIG. 23 is an exploded view of an example of a portion of the MBS 10that includes the light status system. As shown, various structuralcomponents form a portion of the MBS 10 including the light statussystem (e.g., light pipes 72) and the interface 52 when assembled.Specifically, portions of the light status system are structurallyembedded in walls that form the front of the MBS 10. In particular,light pipes 72 are embedded in the three walls of the cavity 44. Thelight pipes 72 channel light from LED boards of an electronics box 74 tothe exterior perimeter of the door frame.

As such, a person on the ground may see LEDs blinking inside the MBS 10because the light is channeled into the light pipes 72 in such a waythat facilitates their visibility by that person. For example, a user ofa mobile device that is connected to the MBS 10 and that experiences anevent (e.g., connection failure) could simply look up to the MBS 10attached to a pole to determine the reason for the event based on theinformation signaled by the light status system.

FIG. 23 shows various other components that have been discussed above orare discussed further below such as the door 46, hinges 58, a housingfor the cable grooves 56, vents (i.e., breathable mesh 50), and aheatsink 32. As indicated above, many of these components may be modularelements of the MBS 10.

The MBS 10 may be a turnkey device that includes hardware, firmware,and/or software components that are operable to function in such a waythat a person with little or no specialized or technical training couldinstall and use the MBS 10. As discussed below, the MBS 10 includesmodular components that can be configured independently and assembled toform a network-in-a-box (NIAB).

As indicated above, the MBS can be representative of a system thatincludes two subsystems: general-baseband computing (GBC) and RFsubsystems. The GBC can further comprise power, housekeepingmicro-controller, timing/sync module, sensors, and control mechanisms.The MBS can be operational as a platform that is designed to takevarious input power sources: PoE (power-over-ethernet), PVC/solar, DC,and external batteries (e.g., sealed lead acid battery) and an internalbattery (e.g., lithium battery). Numerous sensors (e.g., temperature,voltage and current) can be used to ensure that the system is functionalwithin its operating limits.

The following is a non-limiting list of components that could beincluded as part of the hardware design of the MBS:

-   -   OBCC    -   BMS    -   Sensor    -   Controller    -   Sync    -   Processor    -   Front-end    -   RFIC    -   FPGA|SoC    -   PoE|QC|UPS|Solar|DC    -   USB3|Eth|PCIe controller

On the RF sub-system, the MBS can have multiple options based on asoftware-defined radio (SDR) or a system-on-chip (SoC). In someembodiments, the SDR version can support GSM/LTE and run open-sourcesoftware stacks (e.g., openBTS and osmocom for 2G). In some embodiments,the SoC version includes a separate card, and supports commercial LTEsoftware stacks. In some embodiments, the MBS can support twoconfigurations: a full network-in-a-box, when the daughter card iscombined with the GBC board, and alternatively as an access point, whenthe daughter card is operating standalone (in some embodiments, only theSoC version supports this configuration).

Disclosed embodiments of the MBS 10 can include at least one internalquad-band antenna (e.g., antenna 38). As such, the internal antenna 38may operate on all GSM frequency bands. The MBS 10 may be connected toexternal antennas as well or in place of one or more internal antennas38. Electronics and software stored in memory may control the internaland/or external antennas to operate together or independently. Moreover,as indicated above, the antenna (e.g., antenna 38) operates as either anomni antenna or a directional antenna depending on whether the removableplate 42 is attached to the bottom of the MBS.

The architecture of the MBS 10 includes one or more modular circuitboards. For example, FIG. 24 shows a perspective view of one possibleconfiguration of electronics included in an example MBS 10. FIG. 25shows an embodiment of a lateral view of the electronics included in theexample MBS 10. As shown, the example MBS 10 includes two circuitboards: a general-purpose baseband computing (GBC) circuit board 76 anda radio frequency (RF) circuit board 78. These boards are modulecomponents of the MBS 10 and, as such, may be referred to as a GBCmodule and RF module, respectively.

The MBS 10 may be deployed in a variety of configurations. In someembodiments, the MBS 10 may be provided without an RF module 78 and/orGBC module 76. As such, for example, a local operator could supply andport an internal or external RF module (e.g., GSM or LTE module) to theGBC module 76. In some embodiments, multiple MBSs can be deployedwithout RF modules to conserve resources of the GBC modules and,instead, the MBSs could be connected to external devices that provide RFfunctionality via, for example, Ethernet, long-distance Wi-Fi, orsimilar technologies. Lastly, in some embodiments, different radiotechnologies could be utilized simultaneously by connecting a number ofRF modules in a daisy chain configuration to provide the different radiotechnologies to users in the same area.

In the illustrated example embodiment of FIG. 25, the two circuit boards76 and 78 are connected by a single connector 80. The two circuit boards76 and 78 are assembled via “blind mating.” In particular, the GBC board76 is first attached to the heatsink 32 and the RF board 78 is thenconnected to the GBC board 76 via the single connector 80 as the innerenclosure 36 is closed. As such, use of the single connector 80facilitates the blind mating. Moreover, the spacing between the circuitboards 76 and 78 allows for other connectors 68 (e.g., the N-Typeconnectors 68-1 and 68-2) to connect to the circuit boards 76 and 78. Inaddition, shielding (not shown) may be disposed between the circuitboards 76 and 78.

FIG. 26 is a block diagram of an example GBC board or module 76. Asshown, the GBC module 76 includes a microcontroller 82, microprocessor84, board connector 80, Ethernet switch 86, communication components,and power-related components coupled to power connectors.

The microcontroller 82 performs housekeeping functions. Housekeepingfunctions include activating, controlling, managing, and monitoring theGBC and RF portions (if any) of the MBS 10. For example, themicrocontroller 82 activates the microprocessor 84 and the RF module 78,controls switching, and sets frequencies. As such, the microcontroller82 is powered on as soon as the MBS 10 is powered on.

The microcontroller 82 is typically designed to be the most durablecomponent of the GBC module 76. In particular, the microcontroller 82has a power rating and temperature rating that are different from othercomponents, and it prioritizes its operations over the other components.It may monitor temperature, voltages, and the like to ensure properoperations. In the event that a component is malfunctioning, themicrocontroller 82 operates to shut down the malfunctioning componentand notify a local operator about the malfunctioning component via anysuitable communication channel available to the MBS 10.

The microcontroller 82 is coupled to at least one microprocessor 84(e.g., four Intel Atom x86 processors), which is operable to executeinstructions read from memory 88. For example, application or operatingsystem software (e.g., software 90) such as Linux OS executed by themicroprocessor 84 may be stored in and read from the memory 88. Themicroprocessor 84 is also connected to an Ethernet switch 86 forcontrolling Ethernet connectivity.

The board connector 80 physically connects the GBC module 76 and the RFmodule 78. Communication interfaces between the RF module 78 and GBCmodule 76 may include, for example and without limitation, Ethernet,USB2, USB3, PCI-E, GPIOs, and control bits.

The GBC module 76 includes power circuitry 92 coupled to connectors toobtain and/or supply power. As shown, the connectors include the 5-pinconnector 68-5 and the two RJ45 connectors (RJ-1 connector 68-3 and RJ-2connector 68-4). The 5-pin connector 68-5 may be coupled to DC, solar,and external battery power sources. The RJ-1 connector 68-3 may becoupled to a power device to receive power (PoE), and the RJ-2 connector68-4 may be coupled to power source equipment to output power (PoE) toan external device.

The GBC module 76 also includes charge control (QC) and uninterruptedpower supply (UPS) circuitry 94. The GBC module 76 may optionallyinclude an internal battery 96 (e.g., a lithium ion battery). As such,for example, the GBC module 76 may include two charge controllers: onefor the internal battery 96 and the other for the external battery. TheGBC module 76 also optionally includes power bridge circuitry 98 used toswitch between power sources in accordance with policies, hierarchicalrules, and/or circumstances.

The GBC module 76 can auto-detect if the internal battery 96 isinstalled. The internal battery 96 can provide backup power for alimited period of time (e.g., 45 to 60 minutes), allowing themicrocontroller 82 to maintain housekeeping and monitoring operationswhen other power sources are depleted or have failed. As such, the powerbridge circuitry 98 can switch the GBC module 76 to consume power fromthe internal battery 96.

The power bridge circuitry 98 provides several layers of backup power tomaintain an UPS, as discussed further below. In some embodiments, alocal operator can specify the hierarchical rules for automaticallyswitching power sources in the event that another power source isdepleted or fails.

In some embodiments, the light status system of the MBS 10 may signal(i) the state of a power source (e.g., internal battery 96) and/or (ii)a remaining period of operation (e.g., 30 minutes until the internalbattery 96 is depleted). The light status system of the MBS 10 allows alocal operator to diagnose this problem and find an alternate powersource. For example, the MBS 10 could signal that the solar panel ismalfunctioning to prompt the local operator to fix the solar panel.

As shown, the GBC module 76 may also include a synchronization (“sync”)component 100, GSM module 102 (or any suitable communications modulesuch as an LTE module 102), and/or OOBCCs 104, which are discussed infurther detail below. The GBC module 76 may include other componentsknown to persons skilled in the art but not shown or discussed hereinfor brevity, and may, in some embodiments, not include all thecomponents shown.

In some embodiments, the MBS 10 may notify a remote server or service(e.g., cloud-based server or service) of the status of the MBS 10. Forexample, the microcontroller 82 may detect an event and notify themicroprocessor 84 about the event. The microprocessor 84 may utilize theEthernet switch 86 to notify the remote server or service via an RJ45connector.

As indicated above, the MBS 10 includes several layers of power sourcesto provide an UPS. The power sources are connected to the MBS 10 viaphysical power connectors 68. These connectors include the RJ45connectors 68-3 and 68-4 (i.e., ports), the 5-pin connector 68-4 forexternal power sources, and a second connector for the internal battery96. The RJ45 connectors 68-3 and 68-4 and 5-pin connector 68-5 are panelmounted on the interface 52 of the MBS 10.

The first RJ45 connector (RJ-1 connector 68-3) can act to receive PoEfrom both data pair and spare pair components. The second RJ45 connector(RJ-2 connector 68-4) can act as Power Source Equipment (PSE) to supplyPoE to external devices. This functionality allows the MBS 10 to form adaisy chain configuration with other MBSs or a backhaul device (e.g.,CTOS long-distance Wi-Fi), run other devices (e.g., phone chargers), orthe like.

The 5-pin connector 68-5 includes the following pins:

PIN 1 Solar+/AUX+ PIN 2 Solar−/AUX− PIN 3 External BATT+ PIN 4 ExternalBATT− PIN 5 External BATT NTC

In the example embodiment shown, two pins are dedicated to a solar orauxiliary (AUX) power source. As such, these pins provide either AUXpower input or will be connected to solar power. The solar voltage ofthe solar power may, for example, be a maximum of 28V (e.g., range of 5to 28V), and the AUX voltage may, for example, be nominal 24V+/−15%. Thesolar cells providing the solar power may be of 36-cells type. They canhave an open circuit voltage of 21-23V and a maximum voltage ofapproximately 17-18V. The remaining three pins are dedicated to anexternal battery. The external battery could be a standard lead acidbattery at a voltage of 12V, of around 65 Ah capacity.

The connector for the internal battery 96 includes INT BATT+, INT BATT−,and NTC contacts. The internal battery 96 may be a lithium polymerbattery at a voltage of 12.6V, of around 2.7 Ah capacity.

A toggle switch (e.g., power button 66) can be used to power off the MBS10. In some embodiments, when the power button 66 is in the OFFposition, there will be zero or near-zero power drain on the batteriesbecause the MBS shuts down regardless the state of batteries.

The MBS 10 may include power-related circuitry as shown in FIGS. 27 and28, which are block diagrams that show details of example power-relatedcircuitry coupled to components of the MBS 10. In particular, FIG. 27 isa block diagram of an example of a front panel, power supply, andmicrocontroller 82 of the GBC module 76. FIG. 28 is a block diagram ofan example of the front panel, the power supply, the host processor, andthe microcontroller 82 of the GBC module 76.

The power-related circuitry is operable to provide hierarchical powerswitching. For example, FIG. 29 is a table that represents an example ofa possible hierarchy of rules for switching between power sources tofeed a load and charge internal and external batteries. As such, thepower circuitry has an internal “OR-ing” configuration.

As shown in this example, both internal and external batteries arecharged only when the power source is AUX or Solar. If the power sourceis PoE, however, the external battery charging is kept off and only theinternal battery is charged. Specifically, the GBC module'smicrocontroller 82 obtains the information indicating whether a PoE/AUXsource is available and controls charging of the external and internalbatteries accordingly.

In some embodiments, the charging current and/or adapter current couldbe changed and set dynamically based on temperature conditions. Thissetup would help to, for example, minimize the dissipation of heat bythe MBS 10 by controlling how much charging current goes to the externaland internal batteries.

The OOBCCs 104 provide alternate ways to communicate with a remoteserver or service in the event that the backhaul fails. The OOBCCs 104may include a satellite modem that utilizes short burst data tocommunicate events or the status of the MBS 10 with the remote serviceor server. These communications may be bidirectional. As such, a remoteservice can reliably access the MBS 10 to determine its state andstatus.

In some embodiments, the remote server or service can utilize the OOBCCs104 to perform control operations on the MBS 10. For example, in theevent of a security breach, a remote service can remotely erasesubscriber data recorded in memory 88 of the MBS 10 and/or shutdowncomponents. The remote service can utilize the OOBCCs 104 to performthese control operations.

In various embodiments, various power sources can be selected in apriority order when available. As an example, solar power can beprioritized over generator power, which can be prioritized over batterypower. Thus, for example, the most efficient currently available powersource can be used to provide continuous power to the base station.

The MBS 10 may optionally include a GSM or LTE module that provides athird way to route the RF in addition to the internal antenna 38 andexternal antenna. For example, the GSM or LTE module communicates with alocal SIM card to allow a remote service to perform a full local loopback to diagnose the MBS 10, update a patch, resolve billing issues, andthe like. In addition, the GSM or LTE module can communicate with otherMBSs. As such, for example, a remote service can perform full diagnosesof multiple MBSs via a single MBS.

Accordingly, a remote server or service can diagnose events thatoccurred at the MBS 10 or other devices that communicate with the MBS10. For example, the MBS 10 may be linked to a very-small-apertureterminal (VSAT). In the event that the MBS 10 is experiencing acommunications failure, a remote server can send a command to the MBS 10(e.g., via a satellite), which can respond that the MBS 10 isoperational but the VSAT is malfunctioning. The remote server can thensend a message to the local operator that indicates this information andexplains the process for troubleshooting. In addition, the remote servercan monitor the location of the MBS 10 by using the MBS 10's local GPSmeasurements.

The GBC module 76 may also optionally include a synchronizationcomponent 100. The sync component 100 may be another modular component(e.g., separate circuit board) that may be separate from the MBS 10. Thesync component 100 may support multiple protocols with one standardinterface. It may include a GPS subsystem, a high-end oscillator, andvarious other components (e.g., 1PPS, IEEE/588 (PTP), and OCX). In someembodiments, the sync component 100 may include the OOBCCs 104 (whichincludes the short-burst-data satellite modem, e.g., Iridium—tocommunicate with remote servers and local long range communication(e.g., LoRa) to communicate with a local operator).

Referring back to FIGS. 24 and 25, the RF module 78 includes componentsfor performing operations related to radio functions. For example, theRF module 78 includes a digital front end, an analog front end, poweramplifiers, duplexers, and various other components known to personsskilled in the art but not discussed herein for brevity.

The MBS 10 can operate as a GSM, LTE, or any other type of base stationdepending on the type of RF module utilized. In some embodiments, an RFmodule may be provided by a third-party vendor and may be readilyintegrated into the MBS 10. The RF module 78 may include a SoftwareDefined Radio (SDR) and RF System on a Chip (SoC) for GSM, LTE, or anyother RF technology. Each type of RF module may be connected to the sameor its own corresponding GBC module, in the same or different MBSs. Assuch, for example, the RF module 78 of the MBS 10 may be shared withother MBSs that may not have their own RF modules.

In some embodiments, the RF module 78 has a quad-band front end (i.e.,includes a quad-band power amplifier) to support all bands (e.g., at850, 900, 1800, and 1900 MHz). The RF module 78 may include sensors tomonitor various components and, to maintain RF operations, mayautomatically switch between components in the event that any of thecomponents fails. For example, the RF module 78 may include atransceiver or pair of transceivers (TRX) for the low band and a TRX orpair of TRX for the high band. The low band includes frequencies of850-900 MHz and the high band includes those of 1800-1900 MHz. Each TRXhas four amplifiers. The low band TRX operates using two amplifiers, andthe high band TRX operates using two amplifiers. As such, if a low bandamplifier fails, for example, the RF board can switch to the high bandor the low band can operate using the remaining low band amplifiers.

The entire quad-band amplifier may be divided into a number of smallerRF power amplifiers (e.g., 8 smaller RF power amplifiers), rather thanthe conventional single, large power amplifier. The smaller amplifiersprovide redundancy in the event of the failure of any of the smalleramplifiers. Moreover, the smaller RF amplifiers are configurable for aparticular band. For example, four amplifiers could be utilized for thesame band, two different bands could operate at the same time, etc.

The RF module 78 may also include TDMA slot-level duty cyclingtechnology. Specifically, in the GSM slot, an amplifier will be shutdown depending on whether or not there is traffic. This may reduce powerconsumption by each amplifier that is cyclically shut down. For example,when the RF module 78 goes into the duty cycle mode, the entire basestation may consume only about 15 watts.

FIG. 30 is a system diagram showing an example of an implementation ofthe MBS 10 to provide communications between remote servers and mobiledevices. As shown, the system 106 includes the MBS 10, remote servers108, an orbiting satellite 110, a VSAT 112, and one or more mobiledevices 114. These components are interconnected over one or morenetwork links. For example, the orbiting satellite 110, VSAT 112, andthe MBS 10 are network nodes that form links between mobile devices 114,and between the remote servers 108 and the mobile devices 114.

The networks of the system 106 may include any combination of private,public, wired, or wireless portions. The data communicated over thenetworks may be encrypted or unencrypted at various locations or alongdifferent portions of the networks. Each component of the system 106 mayinclude combinations of hardware and/or software to process data,perform functions, communicate over the networks, and the like. Forexample, any component of the system 106 may include a processor, memoryor storage, a network transceiver, a display, an operating system andapplication software (e.g., for providing a user interface), and thelike. Other components, hardware, and/or software included in the systemthat are well-known to persons skilled in the art are not shown ordiscussed herein for brevity.

As detailed above, the MBS 10 is a relatively small, self-contained,portable device that is mountable on poles, trees, or the like. Further,the MBS 10 can provide cellular coverage to regions that may otherwiselack conventional cellular infrastructure. For example, as shown in FIG.30, the MBS 10 is 5 kilometers from a village that includes a number ofhouseholds. The MBS 10 provides coverage that, for example, has a rangeof 5-10 kilometers, which covers the households in the village. As such,the MBS 10 allows the users of the mobile devices 114 to communicatewith each other and/or with the remote servers 108.

The remote servers 108 may include any number of server computersoperable to communicate with the mobile device 114 via the MBS 10 (orOOBCCs). In some embodiments, the remote servers 108 provide a networkportal (e.g., website or other communication channel) that allows themobile devices 114 to access data. In some embodiments, the remoteservers 108 can remotely control, monitor, diagnose, and troubleshootthe MBS 10.

The mobile device 114 may be used by a user to interact with the system.Examples of the mobile device 114 include a smartphone (e.g., AppleiPhone, Samsung Galaxy, Nokia Lumina), a feature phone (e.g., Nokiabrick phone), tablet computer (e.g., Apple iPad, Samsung Note, AmazonFire, Microsoft Surface), computer (e.g., Apple MacBook, Lenovo 440),and any other device that is capable of communicating via the system106.

As shown, information can be communicated in a bidirectional mannerbetween the MBS 10 and the remote servers 108. As such, the remoteservers 108 (e.g., telecom operator or whoever is managing and/ormonitoring the MBS 10) can communicate the information to a localoperator of the MBS 10.

The MBS 10 may include one or more interfaces for communicating over alocal network with a local device. In particular, the MBS 10 may alsoprovide or utilize a Wi-Fi or Long-range WAN (LoRA-WAN) interface as asecondary way to communicate with local devices and/or the remoteservers 108. For example, the MBS 10 may utilize Wi-Fi or LoRA-WAN toestablish a local connection with the VSAT (i.e., a two-way satelliteground station with a small dish antenna) to communicate with the remoteservers 108 via the orbiting satellite 110. As such, the MBS 110 canstill communicate with the remote servers 108 in the event that a radioof the MBS 10 is malfunctioning.

In some embodiments, the MBS 10 may establish a connection with a deviceof a local operator over a Wi-Fi network or LoRA-WAN for troubleshootingpurposes. Wi-Fi typically has a limited range under 200 meters. Incontrast, the LoRA-WAN interface has a broader range. For example, asshown in FIG. 30, the LoRA-WAN may have at least the same range as thebase station coverage area (e.g., 5-10 km). However, use of the LoRA-WANinterface would require a dongle attached to a mobile device of thelocal operator.

In some embodiments, the software design of the MBS can include any ofthe following features:

-   -   BSS-PHYS|L1|L2|L3 . . .    -   Client API    -   Linux    -   Out-of-band Channel    -   Driver    -   BIOS Bootloader    -   BTS-RTOS—Config.|Monitor|Alarm

A cloud-based system could be utilized to synchronize one or more MBSslocated at different sites. For example, FIG. 31 is a block diagram ofan example of a cloud-based system 116 including a client device 118(which may be, for example and without limitation, an MBS 10, or may bea different suitable device) interacting with a cloud-based component120. As shown, the client device 118 communicates over a virtual privatenetwork (VPN) with the cloud component 120 (e.g., remote servers 108 andassociated software). A cloud interconnect (not shown) may connect thecloud component 120 to a public telephone network, VoIP network,messenger, carrier network, or the like (which allows a user to makecalls or perform other communications). In some embodiments, a webinterface (not shown) is provided for configuring components of thecloud-based system 116.

The client device 118 illustrated here may include client software 122,a GSM or LTE stack 124, and a network-in-a-box (NIAB) core 126. As such,the client device 118 can operate as a base station system (BSS), whichcorresponds to a base transceiver station (BTS) and base stationcontroller (BSC) of a GSM network. The cloud component 120 includes astandard SIP core network 128 and a master database 130 of allsubscriber information, usage information, billing data, and the like.

The client software 122 may be stored in memory (in the case of clientdevice 188 being MBS 10, in memory 88) and executes on a microprocessor((in the case of client device 188 being MBS 10, in microprocessor 84)to communicate with the NIAB core 126. The client software 122 mayperform operations related to billing synchronization, subscribermanagement, configuration synchronization, device management (e.g.,determines operations of services at particular times), and the like,with the cloud component 120.

This is commonly referred to as visitor location register (VLR) and maybe included with every client device 118 to allow for local switchingwith all calls and SMS, and can perform these operations for data aswell, for example, by placing the data onto the Internet instead of theSIP core network 128.

These operations may occur online and/or offline. For example, FIG. 32is a flowchart showing an example of a process 3200 performed by theclient device 118 for synchronizing subscriber events with the cloudcomponent 120. In step 3202, the client software 122 of the clientdevice 118 records one or more subscriber events locally while theclient device 118 is operating in an offline mode. Optionally, in step3204, a set of client devices including the client device 118 share aninstance of the client software 122 that obtains subscriber events fromthe set of client devices. Lastly, in step 3206, the client softwareinstance 122 synchronizes the subscriber events with the cloud component120 after the client device 118 is back in an online mode.

Some events that occur at the client device 118 do not require immediatesynchronization with the master database 130. For example, local callsmay proceed without interacting with the cloud component 120, in theevent that the VPN is offline. Once the VPN is back online, a log couldbe sent to the cloud component 120, and the client device 118 could besynchronized with the master database 130.

For example, the client device 118 may cache an entire subscriberdatabase to support local offline operations for billing and subscribermanagement. This includes operations that would normally (e.g., inonline mode) be sent to the remote SIP core network 128. As a result,the client device 118 can support certain functions offline that do notrequire an immediate interaction or check with the cloud component 120,including offline local calls, subscriber mobility, and registration ofnew subscribers. This reduces an amount and/or frequency ofsynchronization between the client device 118 and the remote SIP corenetwork 128.

Some events that occur at the client device 118 require subsequentsynchronization with the master database 130. For example, the clientdevice 118 may need to check with the master database 130 to confirmthat a phone number is available before registering a new subscriber. Assuch, the client device 118 may use API calls for the cloud component120 to perform the subsequent synchronization during an online mode.

A data structure allows the client device 118 to perform local updateswhile offline and synchronize to the cloud component 120 later, and/orpossibly through a peer-to-peer (P2P) network, when online. In someembodiments, every minute, every call or SMS, and the like is handledand routed in this same way.

In some embodiments, each event at each client device 118 is loggedlocally with an associated sequence number. The cloud component 120tracks the highest sequence number that it receives from each and everyclient device. This information can be used in the event thatcommunications are cut off, allowing the cloud component to track whatevents it has already seen (based on their associated sequence numbers).The sequence numbers allow the cloud component 120 to subsequentlyignore events that have already been received and/or reviewed. The cloudcomponent 120 can also monitor the VPN state to detect a downed link. Insome embodiments, the cloud component 120 may also enforce access rightsto limit users in accordance with their subscriptions.

In some embodiments, two or more (e.g., a group or set) of clientdevices 118 utilize a single instance of the client software 122. Thesingle shared client software instance coordinates the states of a setof client devices. For example, FIG. 33 is a block diagram depicting anexample of two sets of client devices 118 whereby each set has a commonbase station component (i.e., shared client software instance).

However, billing information may not be synchronized across multiplesets of client devices 118 or within a single set that has multipleinstances of the client software 122. As such, synchronization may berequired between the multiple instances of the software 122 within a setor across sets (which may have one or more instances of the software 122per set) and the cloud component 120. The synchronization process acrossmultiple sets may in some instances be similar to the process for asingle client device or multiple client devices, as detailed above.Billing and subscription services may be generally handled offline atthe edge of a network (at client devices 118) and then synchronized tothe cloud component 120 when the client devices 118 are back online.

FIG. 34 is a flowchart showing an example of a process 3400 performed bythe cloud component 120 for synchronizing sets of client devices 118. Instep 3402, the cloud component 120 obtains first subscriber events of afirst set of client devices 118. The first subscriber events wererecorded locally by a first shared client software instance while in anoffline mode. In step 3404, the cloud component 120 obtains secondsubscriber events of a second set of client devices 118. The secondsubscriber events were recorded locally by a second shared clientsoftware instance while in an offline mode. Lastly, in step 3406, thecloud component 120 synchronizes the first subscriber events and thesecond subscriber events after going back in an online mode.

In particular, the client devices 118 of a set may each have uplinks, soany client device could be the master and/or perform a switchover tosynchronize with the cloud component 120. In some embodiments, the cloudcomponent 120 can detect which client device 118 per set handles theseoperations. At any time, any client device 118 in a set can be used tosynchronize with the cloud component 120 because there is only onesource of truth per set. As such, the use of one active client softwareinstance within a set avoids the need for synchronization within asingle set of client devices 118.

Synchronization to the cloud component 120 may be optional when a clientdevice 118 can process calls directly with a VoIP provider. In addition,each client device 118 could include a number printed on a side of thedevice to facilitate installation and setup by non-technical users. Forexample, this number could be entered into a website to automaticallyinitialize the VPN and sync for the client device 118.

FIG. 35 is a block diagram of an example computer 132 operable toimplement aspects of the disclosed technology according to someembodiments of the present disclosure. For example, components of thedisclosed systems may include a generic computer or a computerspecifically designed to carry out features of the disclosed technology.For example, the components may include a system-on-chip (SOC), asingle-board computer (SBC) system, a desktop or laptop computer, akiosk, a mainframe, a mesh of computer systems, a handheld mobiledevice, or combinations thereof.

The computer 132 may be a standalone device or part of a distributedsystem that spans multiple networks, locations, machines, orcombinations thereof. In some embodiments, the computer 132 operates asa server computer or a client device in a client-server networkenvironment, or as a peer machine in a peer-to-peer system. In someembodiments, the computer 132 may perform one or more steps of thedisclosed embodiments in any order, in real time, near real time,offline, by batch processing, or combinations thereof.

As shown, the computer 132 includes a bus 134 operable to transfer databetween hardware components. These components include a control 136(i.e., processing system), a network interface 138, an input/output(I/O) system 140, and a clock system 142. The computer 132 may includeother components not shown nor further discussed for the sake ofbrevity. One having ordinary skill in the art will understand anyhardware and software included but not shown in FIG. 35.

The control 136 includes one or more processors 144 (e.g., centralprocessing units (CPUs), application-specific integrated circuits(ASICs), and/or field-programmable gate arrays (FPGAs)) and memory 146(which may include software). The memory 146 may include, for example,volatile memory such as random-access memory (RAM) and/or non-volatilememory such as read-only memory (ROM). The memory 146 can be local,remote, or distributed.

A software program 148, when referred to as “implemented in acomputer-readable storage medium,” includes computer-readableinstructions stored in a memory. A processor is “configured to execute asoftware program” when at least one value associated with the softwareprogram is stored in a register that is readable by the processor. Insome embodiments, routines executed to implement the disclosedembodiments may be implemented as part of the operating system (OS)software (e.g., Microsoft Windows®, Linux®) or a specific softwareapplication, component, program, object, module or sequence ofinstructions referred to as “computer programs.”

As such, the computer programs typically comprise one or moreinstructions set at various times in various memory devices of acomputer and which, when read and executed by at least one processor,cause the computer to perform operations to execute features involvingthe various aspects of the disclosed embodiments. In some embodiments, acarrier containing the aforementioned computer program product isprovided. The carrier is one of an electronic signal, an optical signal,a radio signal, or a non-transitory computer-readable storage medium.

The network interface 138 may include a modem or other interfaces (notshown) for coupling the computer 132 to other computers over a network150. The I/O interface 140 may operate to control various I/O devices,including peripheral devices such as a display system 152 (e.g., amonitor or touch-sensitive display) and one or more input devices 154(e.g., a keyboard and/or pointing device). Other I/O devices 156 mayinclude, for example, a disk drive, printer, scanner, or the like.Lastly, the clock system 142 controls a timer for use by the disclosedembodiments.

Operation of a memory device (e.g., memory 146), such as a change instate from a binary one to a binary zero (or vice versa) may comprise avisually perceptible physical transformation. The transformation maycomprise a physical transformation of an article to a different state orthing. For example, a change in state may involve accumulation andstorage of charge or release of stored charge. Likewise, a change ofstate may comprise a physical change or transformation in magneticorientation, or a physical change or transformation in molecularstructure, such as from crystalline to amorphous or vice versa.

Aspects of the disclosed embodiments may be described in terms ofalgorithms and symbolic representations of operations on data bitsstored on memory. These algorithmic descriptions and symbolicrepresentations generally include a sequence of operations leading to adesired result. The operations require physical manipulations ofphysical quantities. Usually, though not necessarily, these quantitiestake the form of electrical or magnetic signals capable of being stored,transferred, combined, compared, and otherwise manipulated. Customarily,and for convenience, these signals are referred to as bits, values,elements, symbols, characters, terms, numbers, or the like. These andsimilar terms are associated with physical quantities and are merelyconvenient labels applied to these quantities.

While embodiments have been described in the context of fullyfunctioning computers, those skilled in the art will appreciate that thevarious embodiments are capable of being distributed as a programproduct in a variety of forms, and that the disclosure applies equallyregardless of the particular type of machine or computer-readable mediaused to actually effect the distribution.

While the disclosure has been described in terms of several embodiments,those skilled in the art will recognize that the disclosure is notlimited to the embodiments described herein and can be practiced withmodifications and alterations within the spirit and scope of theinvention. Those skilled in the art will also recognize improvements tothe embodiments of the present disclosure. All such improvements areconsidered within the scope of the concepts disclosed herein. Thus, thedescription is to be regarded as illustrative instead of limiting.

The invention claimed is:
 1. A system, comprising: one or more mobiledevices; a modular base station configured to: accept a Long-TermEvolution (LTE) Radio Frequency (RF) modular circuit board; accept aGlobal System for Mobile communication (GSM) RF modular circuit board;provide LTE cellular coverage to the one or more mobile devices whilethe LTE RF modular circuit board is coupled to the modular base station;and provide GSM cellular coverage to the one or more mobile deviceswhile the GSM RF modular circuit board is coupled to the modular basestation; and a mounting bracket for the modular base station, themounting bracket comprising: a first side; a second side perpendicularto the first side, wherein the first side and the second side form asquare bracket configured to secure the mounting bracket to a supportingobject; a holster on the second side; a removable plate configured tofit into the holster; and a rotatable latch configured to secure theremovable plate to the holster.
 2. The system of claim 1, comprising oneor more servers remote from the modular base station, wherein the one ormore servers are configured to: monitor operations of the modular basestation; detect one or more events affecting the operations of themodular base station; diagnose one or more causes of the one or moreevents; and transmit one or more commands to the modular base stationcomprising one or more instructions for troubleshooting the one or morecauses.
 3. The system of claim 2, wherein the instructions comprisehuman-readable instructions.
 4. The system of claim 3, wherein themodular base station comprises a wireless local area network interfaceconfigured to provide out-of-band communications, and the one or moreinstructions are obtained by the modular base station via the wirelesslocal area network interface.
 5. The system of claim 4, comprising atwo-way satellite ground station with a dish antenna, wherein themodular base station is configured to establish a bidirectional linkwith the two-way satellite ground station via the wireless local areanetwork interface.
 6. The system of claim 1, wherein the mountingbracket comprises a plurality of U-bolts configured to secure the firstside to the supporting object.
 7. The system of claim 1, wherein themodular base station, comprises: an outer enclosure configured tointerface with an external environment; an inner enclosure comprisingcircuitry configured to perform network operations, wherein the innerenclosure is enclosed by the outer enclosure and sealed from theexternal environment; and one or more antennas enclosed by the outerenclosure and external to the inner enclosure, wherein the one or moreantennas are communicatively coupled to the circuitry of the innerenclosure and enable wireless communications.
 8. The system of claim 7,wherein the modular base station comprises: a cavity formed by the outerenclosure, a wall of the inner enclosure, a door frame, and a door; andan interface in the cavity, wherein the interface comprises a pluralityof connectors for connecting the circuitry of the modular base stationto one or more external devices.
 9. The system of claim 8, wherein theinterface comprises: one or more N-Type connectors; one or more RJ45connectors; and a multi-pin power connector, wherein the one or moreN-Type connectors are located closer to a center of a flat surfacerelative to the one or more RJ45 connectors and the multi-pin powerconnector.
 10. The system of claim 7, wherein the inner enclosurecomprises: a modular general purpose computing circuit board; and amodular radio frequency circuit board connected to the modular generalpurpose computing circuit board via a single connector.
 11. The systemof claim 7, wherein the modular base station comprises: a perforatedmesh of the outer enclosure, wherein the perforated mesh is permeable tofluid from the external environment; and a removable antenna plateconfigured to be placed on the modular base station, wherein the one ormore antennas are configured to: operate as one or more omni antennaswhile the removable antenna plate is not placed on the modular basestation, and operate as one or more directional antennas while theremovable antenna plate is placed on the modular base station.
 12. Thesystem of claim 8, wherein the door frame comprises: a sloping recessedportion; and a plurality of cable grooves adjacent to the slopingrecessed portion.
 13. The system of claim 8, wherein: a plurality oflight pipes is embedded in a plurality of walls of the door frame; aplurality of lighting sections is located along the door frame; and thelight pipes channel light from the inner enclosure to the plurality oflighting sections.
 14. The system of claim 1, wherein the modular basestation comprises power circuitry operable to switch from a first powersource to a second power source in accordance with predeterminedpolicies or a plurality of hierarchical rules.
 15. The system of claim14, wherein the first power source and the second power source compriseany from a group consisting of: auxiliary power; and solar power. 16.The system of claim 14, wherein the first power source and the secondpower source comprise any from a group consisting of: power overEthernet; battery power from a battery external to the modular basestation; and battery power from a battery internal to the modular basestation.
 17. The system of claim 1, wherein the modular base stationcomprises out-of-band control channel circuitry operable to enablebidirectional communications with the modular base station in accordancewith a wireless local area network protocol.